Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial ADR for IBC client recovery mechanisms #6488

Merged
merged 10 commits into from
Aug 10, 2020

Conversation

cwgoes
Copy link
Contributor

@cwgoes cwgoes commented Jun 23, 2020

Ref cosmos/ibc#421

  • Targeted PR against correct branch (see CONTRIBUTING.md)
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Code follows the module structure standards.
  • Wrote unit and integration tests
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/)
  • Added relevant godoc comments.
  • Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
  • Re-reviewed Files changed in the Github PR explorer

@cwgoes cwgoes added S:proposed x/ibc T: ADR An issue or PR relating to an architectural decision record labels Jun 23, 2020
Copy link
Contributor

@colin-axner colin-axner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, left one comment on handling the updating of the client after the propsoal

Copy link
Collaborator

@fedekunze fedekunze left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. The only comment is to add the default values for the flags and specify the unbending period

@cwgoes
Copy link
Contributor Author

cwgoes commented Jun 23, 2020

To be clarified: how this will interact with potential upgrades (e.g. to a different chain ID). Should we allow this?

Consensus: yes.

Will there be a separate period for the backup upgrade path?

Consensus: no.

@cwgoes
Copy link
Contributor Author

cwgoes commented Jun 23, 2020

Maybe #6378 should also be in this ADR.

@cwgoes
Copy link
Contributor Author

cwgoes commented Jun 25, 2020

Spec issue for epoch number - cosmos/ibc#439 - will wait for spec updates before finalising this ADR.

@fedekunze fedekunze added S:blocked Status: Blocked and removed S:proposed labels Jul 30, 2020
@fedekunze fedekunze added this to the IBC 1.0 milestone Jul 30, 2020
@cwgoes cwgoes dismissed fedekunze’s stale review August 6, 2020 14:58

Comments addressed.

@cwgoes cwgoes removed the S:blocked Status: Blocked label Aug 6, 2020
Copy link
Contributor

@colin-axner colin-axner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. From an implementation point of view, I suppose all we really need in 02-client is to add

Unfreeze() error to ClientState interface.

Then clients can implement arbitrary conditions for unfreezing. It should just be well specified so proposals don't pass that just result in an error.

Copy link
Collaborator

@fedekunze fedekunze left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@cwgoes cwgoes merged commit 769387b into master Aug 10, 2020
@cwgoes cwgoes deleted the cwgoes/architecture-doc-ibc-recovery branch August 10, 2020 16:19
@cwgoes cwgoes mentioned this pull request Aug 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T: ADR An issue or PR relating to an architectural decision record
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants